The following list summarizes important notes with this release:
-
Projects created using Helix QAC (v3.0.0/2021.2 and earlier) are unlikely to analyze without modification - this is due to the replacement of Python 2 with Python 3. See the section Python 3 Migration for more details.
- If you force close Helix QAC, the database daemon will continue to run. However, if Helix QAC is not then run for 12 hours, the daemon will close automatically.
- The intermediate
.viafiles are UTF-8 encoded with a BOM (Byte Order Mark) - Validation of CCTs has been enhanced and a project will only be created or modified if the CCT header is valid. If required you can disable this additional checking by setting the environmental variable
HELIX_QAC_DISABLE_CCT_CHECKSto any value. - If you have a project that was sync-optimized, subsequent syncs that aren't optimized may cause includes and defines to be doubled for the files that are shared between the two runs. Manually removing files in the project before the second sync will resolve this.
- You cannot use components (e.g., parsers such as Helix QAC for C, Helix QAC for C++, etc., and compliance modules such as M3CM, ASCM, etc.) from previous versions of Helix QAC (v2.9.0/2021.1 and earlier) with this version of Helix QAC.